Methods and systems for establishing, hosting and managing a screen sharing session involving a virtual environment

ABSTRACT

Techniques for establishing a screen sharing session are described. Consistent with some embodiments, a web conferencing application executing at a mobile computing device enables a user to specify the identity of a remote computer. The identity of the remote computer is communicated to a web conferencing service, directing the server operating the web conferencing service to establish a remote desktop connection with the remote computer. Once established, the web conferencing service receives from the remote computer a stream of information representing a user interface of the remote computer, and then broadcasts the user interface to all computing devices participating in the web conferencing session, while enabling the mobile computing device to manipulate the user interface of the remote computer.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/313,850, filed Dec. 7, 2011, entitled “Method and Systems forEstablishing, Hosting and Managing a Screen Sharing Session Involving aVirtual Environment,” the benefit of priority of which is herebyclaimed, and which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure generally relates to data processing systems.More specifically, the present disclosure relates to methods, systemsand computer program products for establishing, hosting, and managing ascreen sharing session involving a virtual environment.

BACKGROUND

With various advances in computer and networking technologies, mobilecomputing devices have become smaller, more powerful, full-featured, andomnipresent. In fact, for many working professionals, mobile computingdevices such as mobile handsets (e.g., smart phones) or tablet computingdevices have become the device of choice for everyday computing tasks.Despite the vastly improved performance and feature sets of smart phonesand tablet computing devices, reliance on these mobile computing devicesas one's primary computing device still presents a variety of problemsand technical challenges.

One frequently occurring problem involves using one of these mobilecomputing devices with a web conferencing service to demonstrate thelook, feel and functionality of a software application executing on adesktop computer. For instance, various enterprise software applicationsare designed to reside and execute on desktop computers. Invoking a webconferencing session from the desktop computer on which the enterprisesoftware application is residing and executing allows a web conferencehost to share his or her screen and thereby easily demonstrate thefeatures and functionality of the enterprise software application toparticipants in the web conferencing session. However, when a person isaway from the desktop computer on which the enterprise softwareapplication is residing and executing, and is using a smart phone ortablet computing device as his or her primary computing device,demonstrating how the enterprise desktop application operates via aweb-based conferencing service provides a variety of challenges, some ofwhich are described below in connection with the description of FIG. 1.

FIG. 1 illustrates a conventional approach to using a mobile computingdevice (e.g., such as a tablet computer 10) to demonstrate toparticipants in a web conferencing session the look, feel andfunctionality of a software application residing and executing on acomputer 16 that is remote from the mobile computing device 10. Asillustrated in FIG. 1, a first participant referred to as the webconference host 12 is shown to be operating a mobile computing device(e.g., tablet computer 10). In addition, as indicated by the dotted linewith reference number 14, the web conference host 12 is authorized touse a remote desktop computer 16 on which resides an enterprise softwareapplication. In order to demonstrate to various web conferenceparticipants the look, feel and functionality of the enterprise softwareapplication executing on the desktop computer 16, the web conferencehost 12 first invokes a web conferencing application on the tabletcomputer 10. For instance, using a tablet-based web conferencingapplication, the host specifies the participants to be invited to theweb conference, communicates invitations to the participants, and theninitiates the web conferencing session with the server hosting the webconferencing service 18. Accordingly, with the web conferencingapplication residing on the tablet computer 10, the web conference host12 establishes a web conferencing session with one or more remoteparticipants 20, 22 and 24. This operation is represented in FIG. 1 bythe line (with reference number 1 enclosed in a circle) connecting thetablet computer 10 to the server executing the web conferencing service18.

Next, the web conference host 12 uses a second application residing andexecuting at the tablet computer 10 to establish a remote desktopconnection with the remote desktop computer 16 on which the enterprisesoftware application is residing and executing. This operation isrepresented in FIG. 1 by the line (with reference number 2 enclosed in acircle) connecting the tablet computer 10 with the remote desktopcomputer 16. The remote desktop connection enables the web conferencehost 12 to use the touch screen display of the tablet computer 10 toview and interact with the desktop interface of the remote desktopcomputer 16. Accordingly, once the remote desktop connection isestablished, the web conference host 12 can use the input mechanisms ofthe tablet computer 10 to manipulate the interfaces of various softwareapplications residing and executing at the remote desktop computer 16,including the software application to be demonstrated.

Finally, using the remote desktop connection between the tablet computer10 and the remote desktop computer 16, the web conference host 12invokes a web conferencing application on the remote desktop computer16, and causes the remote desktop computer 16 to join the webconferencing session as a participant. The line with reference number 3enclosed in a circle represents this operation. By manipulating thesettings of the web conferencing application, either at the tabletcomputer 10 or at the remote desktop computer 16, the web conferencehost 12 can select the screen of the remote desktop computer 16 to bebroadcast to all participants in the web conferencing session.Consequently, when the web conference host 12 uses the remote desktopconnection between the tablet computer 10 and the remote desktopcomputer 16 to manipulate the interface of the enterprise softwareapplication residing and executing at the remote desktop computer 16,the user interface of the enterprise software application is broadcastvia the screen sharing feature of the web conferencing service 18 to allweb conference participants, including remote participants 20, 22, and24.

Although the above-described technique generally achieves the desiredobjective—that is, sharing or broadcasting the screen of the remotedesktop computer 16 while the web conference host 12 manipulates theinterface of the enterprise software application—a number of problemsarise with this general approach and technique. First, the remotedesktop application residing and executing at the tablet computer 10generally does not provide an optimal interface for manipulating theuser interface of the software applications residing and executing onthe remote desktop computer 16. Specifically, tablet computers withtouch screen displays that rely primarily on a touch interface as ameans of receiving user input do not provide very good control overdesktop applications that generally rely on receiving input via apointing device (e.g., computer mouse, or track pad) and/or keyboard.Second, because the web conference host 10 must establish and manage theweb conference via a first tablet-based application, and then establishand manage the remote desktop session through a second tablet-basedapplication, the web conference host 12 is required to switch back andforth between the two applications, as necessary, to perform therequired tasks. With many mobile computing devices, switching back andforth between applications, if possible at all, is a time consuming andclunky process at best. Finally, as the tablet computer 10 is requiredto establish separate communication sessions for both the webconferencing application and the remote desktop application, thistechnique for screen sharing requires that significant network bandwidthbe available to the tablet computer 10. Because the tablet computer ismobile and may be located where wireless network access and bandwidthare limited, the bandwidth requirements for establishing and supportingboth communication sessions may be difficult to satisfy.

DESCRIPTION OF THE DRAWINGS

Some embodiments of the invention are illustrated by way of example andnot limitation in the figures of the accompanying drawings, in which:

FIG. 1 is a block diagram illustrating a computer network environment inwhich a mobile computing device is used to establish and controlseparate communication sessions (e.g., web conferencing session andremote desktop session) for the purpose of performing a screen sharingoperation, consistent with conventional techniques;

FIG. 2 is a block diagram illustrating a computer network environment inwhich a mobile computing device executing a web conferencingapplication, consistent with an embodiment of the invention, is used toestablish a web conferencing session with a web conferencing service,and to direct the web conferencing service to establish a remote desktopconnection with a remote computer, thereby allowing the user interfaceof the remote computer to be broadcast and shared with web conferenceparticipants;

FIGS. 3A and 3B are functional block diagrams illustrating examples of aweb conferencing application for execution on a mobile computing device,and a web conferencing service, respectively, consistent withembodiments of the invention;

FIG. 4 is a flow diagram illustrating the method operations performed bya mobile computing device executing a web conferencing application aspart of a method for establishing and managing a screen sharing session,according to some embodiments of the invention;

FIG. 5 is a flow diagram illustrating the method operations performed bya server operating a web conferencing service as part of a method forestablishing and managing a screen sharing session using a remotedesktop connection, according to some embodiments of the invention; and

FIG. 6 is a block diagram of a machine in the form of a computing devicewithin which a set of instructions, for causing the machine to performany one or more of the methodologies discussed herein, may be executed.

DETAILED DESCRIPTION

The present disclosure describes methods, systems, and computer programproducts, which individually provide functionality for establishing,hosting, and managing a screen sharing session involving a virtualenvironment. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the various aspects of different embodiments of thepresent invention. It will be evident, however, to one skilled in theart, that the present invention may be practiced without all of thespecific details.

For purposes of the present disclosure, a “web conferencing service” isany computer-based service that allows two or more participants tocommunicate and/or exchange information, including audio, video andgraphical information, over a network. A web conferencing service allowsinformation to be shared simultaneously, across geographically dispersedlocations in real-time, or near real-time. As such, a web conferencingapplication allows for conducting meetings, training events, lectures orshort presentations from a computer. Communications and informationexchanged between the participants in a web conferencing session may bebroadcast to all participants, or in some cases, communications andinformation may flow in only one direction (e.g., from ahost-participant to all other participants), such as the case might bewith a web-based seminar (frequently referred to as a webinar). Thepresent inventive subject matter is applicable to any and all of theaforementioned web conferencing services, systems and applications.

Screen sharing, which is a particular feature made possible by webconferencing services, allows a participant in a web conferencingsession to share the user interface being displayed on the display ofthe participant's computing device. As such, a “screen sharing session”involves broadcasting a user interface displayed at a computing deviceto one or more other computing devices, thereby enabling remote webconferencing participants to view the user interface being presented onthe display or screen of a computing device that is remote from the webconferencing participants. As described in greater detail below, withembodiments of the present invention a screen sharing session can beinvoked and controlled with a mobile computing device (e.g., a tabletcomputer or smart phone), where the user interface that is being shared(e.g., broadcast to the web conference participants) is the userinterface of a computer that is remote from the mobile computing deviceand communicatively coupled to a web conferencing service via a remotedesktop connection (e.g., a virtual environment).

For purposes of the present disclosure, the terms “web conference host”and “host-participant” are used synonymously to identify and distinguishthe particular conference participant(s) who will generally haveprivileges and access to functionality that are not available to regular(i.e., non-host) participants. Specifically, consistent with at leastsome embodiments, a host-participant will have both the ability and theauthority to provide the identity (e.g., hostname or Internet Protocol(IP) address) of a remote computer, for the purpose of requesting thatthe web conferencing service establish a remote desktop connection withthe remote computer, thereby enabling the host-participant to view andmanipulate the interface or desktop of the remote computer via thehost-participant's computing device while the interface is beingbroadcast to all web conference participants. More generally, ahost-participant will be able to organize and initiate a webconferencing session, for example, by specifying the identities ofpersons who are to be invited to participate in the web conferencingsession. Additionally, a computer or computing device that is being usedby a web conferencing host or host-participant is referred to herein asa “host-computing device,” whereas a non-host participant's computer orcomputing device is referred to simply as a “participant-computingdevice.” As described below, with some embodiments of the invention, thehost-computing device is a mobile computing device, such as a smartphone or tablet computer. However, with some embodiments, thehost-computing device may be a conventional desktop computer, laptopcomputer, or a computing device with any other form factor.

Consistent with various embodiments of the invention, and as describedin greater detail below, a web conferencing application residing andexecuting on a mobile computing device (e.g., such as a smart phone, ortablet computer) provides functionality that enables a user to veryeasily and quickly share with participants in a web conferencing sessionthe view of a user interface or desktop interface of a remote,network-connected computer. For example, by simply specifying, via theuser interface of the web conferencing application at the mobilecomputing device, the identity (e.g., hostname or Internet Protocol (IP)address, or other identifying means) of a remote, network-connectedcomputer, the user can invoke a command and direct a server executing aweb conferencing service to establish a remote desktop connection withthe remote computer. Once the remote desktop connection is establishedbetween the server and the remote computer, the desktop interface of theremote computer is received at the server, and then broadcast via theweb conferencing service to each web conference participant's computingdevice, thereby allowing each participant to view the user interface ordesktop interface of the remote computer. Additionally, the webconferencing service provides a control interface that allows a user ofthe mobile computing device to not only view the remote desktopinterface, but also to interact with the remote desktop interface viathe various input mechanisms of the mobile computing device on which theweb conferencing application is executing.

Because the mobile computing device on which the web conferencingapplication is executing need only establish a single communicationsession with the web conferencing service, the bandwidth requirementsfor sharing the remote desktop interface are reduced from what isrequired with many conventional approaches. Moreover, the webconferencing application residing and executing at the mobile computingdevice can be optimized to take advantage of native input and controlmechanisms to control the remote desktop interface. Specifically, withsome embodiments, the web conferencing application will leverageapplication programming interfaces (API's) associated with the mobilecomputing device to allow for interaction with and control of the remotedesktop interface via the mobile computing device's various input andcontrol mechanisms, for example, to include any one or more of: touchscreen displays, microphones, various location sensing devices (e.g.,global positioning system (GPS)) and orientation sensors (e.g.,accelerometers and gyroscopes), and others. Finally, because the webconferencing application on the mobile computing device provides thefunctionality to cause the server, on which the web conferencing serviceis executing, to establish the remote desktop connection with the remotecomputer, the user of the mobile computing device need not switch backand forth between separate and distinct applications for establishingthe web conferencing session, and establishing the remote desktopconnection. Other advantages and aspects of the inventive subject matterwill be readily apparent from the description of the figures thatfollows.

FIG. 2 is a block diagram illustrating a computer network environment 30in which a mobile computing device 32 executing a web conferencingapplication, consistent with an embodiment of the invention, is used toestablish a web conferencing connection (or session) 34 with a webconferencing service 36, and to direct the web conferencing service 36to establish a remote desktop connection (or session) 38 with a remotecomputer 40, thereby allowing the user interface of the remote computer40 to be broadcast and shared with web conference participants 42, 44,and 46. Although the mobile computing device 32 being operated by theweb conference host in the example of FIG. 1 is presented as a tabletcomputer, in other embodiments of the invention the client computingdevice of the web conference host might be any type of computer, havingany number of form factors, to include desktop, laptop, and notebookcomputers, as well as a variety of other more application-specificdevices, such as computing devices developed specifically for web/videoconferencing, set top boxes and/or televisions with web/videoconferencing functionality, mobile handsets or smart phones, and soforth.

For purposes of the example being presented in FIG. 2, one can presumethat the web conference host using a web conferencing applicationexecuting on the mobile computing device 32 desires to demonstrate, tothe web conference participants 42, 44 and 46, a software applicationthat is residing at the remote desktop computer 40. Accordingly, the webconference host invokes a web conferencing application residing on hisor her mobile computing device (e.g., the tablet computer with referencenumber 32). Using the web conferencing application executing on themobile computing device 32, the web conference host initiates or invokesa web conferencing session and establishes a web conferencing connection34 between the mobile computing device 32 and the web conferencingservice 36. This may involve sending out invitations (e.g., by email orother messaging service) to the web conference participants, oralternatively, simply invoking a command to initiate the webconferencing session, if the web conferencing session parameters (e.g.,list of participants, scheduled time, and any additional resources) havealready been defined.

After the web conferencing session has been initiated and each webconference participant 42, 44 and 46 has established a communicationsession with the web conferencing service 36 with his or her respectivecomputing device, the participants will be able to exchange informationwith one another. For instance, with some embodiments, the webconferencing service may facilitate audible communication via any numberof communication services and/or protocols that facilitate suchcommunications over an Internet Protocol (IP) network, such as VoiceOver IP (VOIP). With some embodiments, the web conferencing service 36may integrate with a telephony server (not shown), enabling participantsto use conventional landline telephones to establish an audibleconnection with the other participants. Accordingly, with someembodiments, the web conferencing service 36 may allow a mix of IP-basedcommunications, and conventional analog telephone communications.

In addition to facilitating audible communications, the web conferencingservice 36 may also facilitate the exchange of graphical or videoinformation, for example, via one or more video-based communicationprotocols, to include, any one of the following: Real Time MessagingProtocol (RTMP), Real Time Media Flow Protocol (RTMFP), Real-timeTransport Protocol (RTP), or Hypertext Transport Protocol (HTTP). Usingone of the aforementioned protocols, and a video codec, such as H.264,one of the On2 TrueMotion codecs (e.g., VP6, VP7 or VPA), the SorensonSpark video codec (also known as Sorenson H263 or FLV1), the vlib videocodec, or some other similar video codec, a data stream received at theweb conferencing service from one computing device may be broadcast tothe computing devices of all web conference participants. With someembodiments, using a control interface of the web conferencingapplication, the web conference host may choose to share a userinterface being presented at the mobile computing device 32, or the userinterface of a particular application executing at the mobile computingdevice 32. In some embodiments, more granular control may enable a webconference host to specify a particular window, or other graphical userinterface element of an application, that is to be broadcast to theother participants. Additionally, at least with some embodiments, theweb conference host may authorize another web conference participant toshare (e.g., broadcast) information being presented on his or herdisplay screen.

If, during the web conferencing session, the web conference host desiresto demonstrate the look, feel and functionality of a softwareapplication that is residing on the remote computer 40, the webconference host can very easily establish a remote desktop connectionwith the remote computer 40 via the web conferencing applicationexecuting on the mobile computing device 32, and thus share the screenor user interface of the remote computer 40 with the other participants42, 44 and 46. For instance, during the web conferencing session, theweb conference host may manipulate a control interface of the webconferencing application on the mobile computing device 32, therebyenabling the web conference host to select or otherwise specify theidentity (e.g., hostname or IP address) of the remote computer 40. Bypressing a button or interacting with some other graphical userinterface element, the web conference host causes the web conferencingapplication to communicate a command over the network, with the identityof the remote computer, to the web conferencing service 36. This commanddirects the web conferencing service 36 to use the hostname or IPaddress of the remote computer to establish a remote desktop connection38 with the remote computer 40. In some instances, the web conferencehost may have previously specified the identity of the remote computer40 at the time the initial parameters for the web conferencing sessionwere established. In such instances, the web conference host may simplyinteract with a graphical user interface element presented on the touchscreen display of the mobile computing device, or simply speak a commandto the mobile computing device 32, to direct the web conferencingservice 36 to use the previously provided parameters to establish theremote desktop connection 38 with the remote computer 40.

In some instances, the web conferencing service 36 may prompt the webconference host to enter or otherwise provide authorization information(e.g., username and password) for establishing the remote desktopconnection with the remote computer 40. The web conference host mayprovide the authorization information via a user interface of the webconference application executing at the mobile computing device 32.Alternatively, in some instances, the web conference host may havepreviously provided the authorization information as part of the set-upand configuration process when providing the other parameters for theweb conference session. If setup in advance, the parameters for the webconferencing session may be provided via any network-connected computer,to include the mobile computing device 32.

In any case, when the web conference host directs the web conferencingservice 36 to establish the remote desktop connection 38, the webconferencing service 36 will communicate directly (e.g., via a network)with the remote computer 40 to establish the remote desktop connection38. In the context of the present disclosure, a remote desktopconnection is a connection established with a software application or anoperating system feature that allows applications to be executedremotely (i.e., on a remote computer), while being displayed locally, ona locally operated computer. The desktop or user interface of the remotecomputer 40 is communicated to and received at the web conferencingservice 36 via the remote desktop connection 38, converted or transcodedfor broadcasting to the web conference participants, 42, 44 and 46, andthen broadcast to the computing devices of the participants for displayon their respective computing devices 42, 44 and 46. Various embodimentsof the invention use any one of several remote connection protocols toestablish the remote desktop connection between the web conferencingservice 36, and the remote computer 40. Examples of these remoteconnection protocols include: Remote Desktop Protocol (RDP), IndependentComputing Architecture (ICA), Remote FrameBuffer (RFB), or VirtualNetwork Computing (VNC), as well as other proprietary or non-proprietaryprotocols that serve the same or similar functions.

Once the remote desktop connection 38 is established, agent software(e.g., a remote connection software application) residing on the remotedesktop computer 40 will communicate information representing thedesktop user interface of the remote computer 40 to the web conferencingservice 36, which will in turn, convert or transcode the informationinto a format suitable for broadcasting to the computing devices of allweb conference participants. For example, the web conferencing service36 will convert the information representing the user interface of theremote computer from a format consistent with one of the aforementionedremote connection protocols, to a format consistent with one of theaforementioned web conferencing (or, video) protocols. Once transcoded,the information stream received from the remote computer 40 is broadcastto the computing devices of the web conference participants.

In addition to simply broadcasting the information representing the userinterface of the remote computer 40, the web conferencing serviceincludes a control interface via which it can receive input from the webconferencing application executing at the mobile computing device. Forexample, with some embodiments, by default the web conferencingapplication of the web conference host will be authorized to communicatecommands to the remote computer 40. Accordingly, the web conference hostcan use the mobile computing device 32 to manipulate the user interfaceof the remote computer, while the user interface of the remote computeris being broadcast to all web conference participants. In this mannerthe web conferencing service 36 facilitates a screen sharing sessionwith a computer that is coupled to the web conferencing service via aremote desktop connection (a virtual environment) and can be manipulatedvia a remote, network-connected, mobile computing device.

FIGS. 3A and 3B are functional block diagrams illustrating examples of aweb conferencing application 50 for execution on a mobile computingdevice 32, and a web conferencing service 36, respectively, consistentwith embodiments of the invention. As illustrated in FIG. 3A, the webconferencing application 50 resides and executes on a mobile computingdevice 32, and includes a remote desktop interface module 52. Thisremote desktop interface module 52 may leverage one or more applicationprogramming interfaces (APIs) 54 of the operating system 56 of themobile computing device. Accordingly, the web conferencing host caninteract with the remote desktop interface using various inputmechanisms that are native to the mobile computing device. As such,controlling the remote desktop interface becomes much more intuitive,because the interface is customized (using the APIs) to take advantageof the native input mechanisms. For instance, with many mobile computingdevices, the primary input mechanism is a multi-touch, touchscreendisplay. By leveraging the APIs associated with the underlying operatingsystem of the mobile computing device, user input events detected viathe mobile computing device's input mechanisms can be converted toinputs or commands suitable for processing by the application executingat the remote computer.

FIG. 3B illustrates an example of the various functional modulesincluded in a web conferencing service, consistent with some embodimentsof the invention. In particular, as illustrated in FIG. 3B, the webconferencing service consists of two primary modules, including the webconference engine 58 and the web conference management module 60. Theweb conference management module 60 facilitates various functions forsetting up and configuring a web conferencing session. With someembodiments, the web conferencing service 36 includes a web server (notshown) by which it can receive and send information. For example, atleast with some embodiments, the web conference management module 60receives from a web conferencing application 50 information for use insetting-up or configuring a web conferencing session. The webconferencing application may be a web-based application, or may be adesktop, mobile or tablet-specific application. In any case, theinformation that is communicated to the web conference management module60 to setup a web conferencing session may include the identities (e.g.,names, email addresses, telephone numbers, or some other identifyinginformation) of the persons to be invited to participate in the webconferencing session. To authorize or verify the identity of theparticipants prior to allowing participation in a web conferencingsession, the web conference management module includes a participantauthorization module 62. In addition, the information may specify a timeand date when the web conferencing session is to occur. The informationmay also specify various parameters concerning the features andresources to be made available with the web conferencing session. Forexample, with some embodiments, participants may have several optionsfor accessing audio information during the web conferencing session.With at least with some embodiments, a web conference host may identifya computer with which the web conferencing service 36 is to establish aremote desktop connection during the web conferencing session, therebyenabling the web conference host to manipulate and share the userinterface of the remote computer with all web conference participants.

The web conference engine 58 includes the various modules that enablethe exchange of information between participants during a webconferencing session. Specifically the web conference engine 58 includesa video broadcast module 64 for receiving information representing auser interface of a desktop software application, and then broadcastingthe user interface to all participants in the web conferencing session.Accordingly, if a web conference host is using a desktop computer toparticipate in the web conferencing session, the web conference host canshare his or her screen or display to demonstrate the look, feel andfunctionality of a software application executing on the web conferencehost's computer. Similarly, if the web conference service hasestablished a remote desktop connection with a remote computer, the userinterface of the remote computer, upon being received (e.g., by thelistener module 68), and converted or transcoded (e.g., by thetranscoder module 70), can be broadcast to all web conferenceparticipants by the video broadcast module 64.

In certain situations, the web conference host may be using a mobilecomputer (e.g., a tablet computer or smart phone), or a computer thatdoes not have the particular software application that the webconference host would like to demonstrate to the other web conferenceparticipants. Consequently, the web conference host can specify theidentity of a remote computer on which the software application resides.As illustrated in FIG. 3B, the remote desktop connection module 66, wheninvoked, will attempt to establish a remote desktop connection with theremote computer identified by the web conference host. The webconference host can specify the remote computer prior to, or during, aweb conferencing session. Upon establishing a remote desktop connectionwith the remote computer identified by the web conference host, thelistener module 68 of the remote desktop connection module 66 willreceive a stream of information representing a user interface of theremote computer. For example, the user interface may be that of thedesktop, or of a particular software application being executed at theremote computer. The transcoder module 70 transcodes, or converts, thereceived information from one format to another that is suitable forbroadcasting or communicating to the computing devices of the webconference participants. Finally, the broadcast module 72 broadcasts thenow converted information to the computing devices of the web conferenceparticipants, allowing all web conference participants to view the userinterface of the remote computer.

During the broadcasting of the user interface of the remote computer,the web conference host can use the web conferencing applicationresiding and executing on the mobile computing device to provideuser-inputs that control or manipulate the user interface of the remotecomputer. For instance, these user-inputs generate commands that arecommunicated to the control interface 74 of the remote desktopconnection module 66, which will in turn forward the commands to theremote computer for processing.

As described briefly above, with various embodiments of the invention,the remote desktop connection module 66 of the web conference engine 58will use any one of several different remote connection protocols toestablish the remote desktop connection between the web conferencingservice 36, and the remote computer 40. While the following list is byno means exhaustive, examples of these remote connection protocolsinclude: Remote Desktop Protocol (RDP), Independent ComputingArchitecture (ICA), Remote FrameBuffer (RFB), or Virtual NetworkComputing (VNC), as well as other proprietary or non-proprietaryprotocols that serve the same or similar functions. In turn, thetranscoder module 70 will receive and transcode, or convert, the userinterface information that is received in a format consistent with oneof the above protocols into a format consistent with a video protocol.While the following list of video protocols is not exhaustive, examplesinclude: H.264, or, one of the On2 TrueMotion codecs (e.g., VP6, VP7 orVPA). Finally, the encoded video, representing the user interface of theremote computer, is broadcast to the various computing devices of theweb conference participants using any one of the following protocols:Real Time Messaging Protocol (RTMP), Real Time Media Flow Protocol(RTMFP), Real-time Transport Protocol (RTP), or Hypertext TransportProtocol (HTTP).

FIG. 4 is a flow diagram illustrating the method operations performed bya mobile computing device executing a web conferencing application aspart of a method for establishing and managing a screen sharing session,according to some embodiments of the invention. Consistent with themethod 80 illustrated in FIG. 4, during a web conferencing session, aweb conference host manipulates a control interface of a webconferencing application. Specifically, the web conference host causesthe web conferencing application, at method operation 82, to present auser interface element (e.g., such as a text entry box, or similarelement), and a prompt to provide or enter the identity of a remotecomputer with which the web conferencing service is to establish aremote desktop connection.

Next, at method operation 84, the web conferencing application executingon the computing device of the web conference host receives the identityof the remote computer. The identity may be specified as a hostname, oran Internet Protocol (IP) address, or some other identifier that can beproperly resolved to uniquely identify the remote computer with whichthe web conferencing service is to establish a remote desktopconnection. At method operation 86, the web conferencing applicationcommunicates the identity of the remote computer to the server operatingthe web conferencing service. The identity of the remote computer iscommunicated to the server with, or as part of, a command directing theserver to invoke or establish the remote desktop connection with theremote computer. Finally, at method operation 88, the web conferencingapplication residing and executing on the web conference host'scomputing device receives a stream of information from the serveroperating the web conferencing service. The stream of information, whichis being broadcast to all web conference participants, represents theuser interface of the remote computer.

FIG. 5 is a flow diagram illustrating the method operations performed bya server operating a screen sharing or web conferencing service as partof a method for establishing and managing a screen sharing session usinga remote desktop connection, according to some embodiments of theinvention. As illustrated in FIG. 5, the method begins at operation 92when a web conferencing session is established between a host-computingdevice and at least one participant-computing device. Via the webconferencing session, at least with some embodiments, the web conferenceparticipants will be able to exchange information, such as audibleinformation. Next, at method operation 94, the server operating the webconferencing service receives from the host-computing device theidentity of a remote, network-connected computer, with which the serviceis to establish a remote desktop connection. For instance, in responseto receiving the hostname, or IP address, of the remote computer, theserver operating the web conferencing service establishes a remotedesktop connection with the remote computer.

At method operation 96, the server operating the web conferencingservice receives from the remote computer, via the remote desktopsession, a stream of information representing a user interface of theremote computer. Finally, at method operation 98 the received stream ofinformation is converted into a format suitable for broadcasting via theweb conferencing session, and then broadcast to the computing devices ofthe respective web conference participants.

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedmodules, engines, objects or devices that operate to perform one or moreoperations or functions. The modules, engines, objects and devicesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules, engines, objects and/or devices.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or more processors orprocessor-implemented modules. The performance of certain operations maybe distributed among the one or more processors, not only residingwithin a single machine or computer, but deployed across a number ofmachines or computers. In some example embodiments, the processor orprocessors may be located in a single location (e.g., within a homeenvironment, an office environment or at a server farm), while in otherembodiments the processors may be distributed across a number oflocations.

FIG. 6 is a block diagram of a machine in the form of a computer systemor computing device within which a set of instructions, for causing themachine to perform any one or more of the methodologies discussedherein, may be executed. In alternative embodiments, the machineoperates as a standalone device or may be connected (e.g., networked) toother machines. In a networked deployment, the machine may operate inthe capacity of a server or a client machine in a client-server networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. In some embodiments, the machine will be a desktopcomputer, or server computer, however, in alternative embodiments, themachine may be a tablet computer, a mobile phone, a personal digitalassistant, a personal audio or video player, a global positioningdevice, a set-top box, a web appliance, or any machine capable ofexecuting instructions (sequential or otherwise) that specify actions tobe taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The example computer system 1500 includes a processor 1502 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 1501 and a static memory 1506, which communicatewith each other via a bus 1508. The computer system 1500 may furtherinclude a display unit 1510, an alphanumeric input device 1517 (e.g., akeyboard), and a user interface (UI) navigation device 1511 (e.g., amouse). In one embodiment, the display, input device and cursor controldevice are a touch screen display. The computer system 1500 mayadditionally include a storage device 1516 (e.g., drive unit), a signalgeneration device 1518 (e.g., a speaker), a network interface device1520, and one or more sensors 1521, such as a global positioning systemsensor, compass, accelerometer, or other sensor.

The drive unit 1516 includes a machine-readable medium 1522 on which isstored one or more sets of instructions and data structures (e.g.,software 1523) embodying or utilized by any one or more of themethodologies or functions described herein. The software 1523 may alsoreside, completely or at least partially, within the main memory 1501and/or within the processor 1502 during execution thereof by thecomputer system 1500, the main memory 1501 and the processor 1502 alsoconstituting machine-readable media.

While the machine-readable medium 1522 is illustrated in an exampleembodiment to be a single medium, the term “machine-readable medium” mayinclude a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more instructions. The term “machine-readable medium” shallalso be taken to include any tangible medium that is capable of storing,encoding or carrying instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresent invention, or that is capable of storing, encoding or carryingdata structures utilized by or associated with such instructions. Theterm “machine-readable medium” shall accordingly be taken to include,but not be limited to, solid-state memories, and optical and magneticmedia. Specific examples of machine-readable media include non-volatilememory, including by way of example semiconductor memory devices, e.g.,EPROM, EEPROM, and flash memory devices; magnetic disks such as internalhard disks and removable disks; magneto-optical disks; and CD-ROM andDVD-ROM disks.

The software 1523 may further be transmitted or received over acommunications network 1526 using a transmission medium via the networkinterface device 1520 utilizing any one of a number of well-knowntransfer protocols (e.g., HTTP). Examples of communication networksinclude a local area network (“LAN”), a wide area network (“WAN”), theInternet, mobile telephone networks, Plain Old Telephone (POTS)networks, and wireless data networks (e.g., Wi-Fi® and WiMax® networks).The term “transmission medium” shall be taken to include any intangiblemedium that is capable of storing, encoding or carrying instructions forexecution by the machine, and includes digital or analog communicationssignals or other intangible medium to facilitate communication of suchsoftware.

Although an embodiment has been described with reference to specificexample embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader spirit and scope of the invention. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense. The accompanying drawings that form a parthereof, show by way of illustration, and not of limitation, specificembodiments in which the subject matter may be practiced. Theembodiments illustrated are described in sufficient detail to enablethose skilled in the art to practice the teachings disclosed herein.Other embodiments may be utilized and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. This Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

What is claimed is:
 1. A web conferencing system comprising: one or moreprocessors of a web conferencing server; and one or more computerstorage media storing computer-executable instructions that, whenexecuted by the one or more processors, implement a method comprising:establishing a web conferencing session including a host computingdevice and a participant computing device, receiving a request from thehost computing device to establish a remote desktop connection with aremote computing device, wherein the remote desktop connection providesfor sharing a graphical user interface that is generated by the remotecomputing device for presentation at a display of the remote computingdevice, receiving from the host computing device an indication of anidentity of the remote computing device, wherein the indication of theidentity of the remote computing device is received from the hostcomputing device based on a prompt for information identifying theremote computing device, based on the request to establish the remotedesktop connection with the remote computing device and on theindication of the identity of the remote computing device, establishingthe remote desktop connection with the remote computing device, andbased on the remote desktop connection, sharing the graphical userinterface that is generated by the remote computing device with the hostcomputing device and the participant computing device.
 2. The webconferencing system of claim 1, wherein the remote computing devicecomprises a desktop computer, and wherein the graphical user interfaceis generated based on a software application executing at the desktopcomputer.
 3. The web conferencing system of claim 2, wherein the hostcomputing device comprises a mobile computing device.
 4. The webconferencing system of claim 3, wherein the mobile computing devicecomprises at least one of a mobile phone or a tablet.
 5. The webconferencing system of claim 1, wherein the method further comprises: atthe web conferencing server, receiving, from the host computing device,an indication of an input intended for a software application executingat the remote computing device, and based on the indication of theinput, communicating a command to the remote computing device.
 6. Theweb conferencing system of claim 5, wherein the software applicationexecuting at the remote computing device is controlled based on theinput provided at the host computing device.
 7. The web conferencingsystem of claim 6, wherein the input provided at the host computingdevice is provided via a graphical user interface associated with a webconferencing application executing at the host computing device.
 8. Acomputer-implemented method comprising, at a server computer:establishing a web conferencing session including a host computingdevice and a participant computing device; receiving, from the hostcomputing device, a request to establish a remote desktop connectionwith a remote computing device, the request comprising an indication ofan identity of the remote computing device, wherein the indication ofthe identity of the remote computing device is received from the hostcomputing device based on a prompt for information identifying theremote computing device; based on the request to establish the remotedesktop connection with the remote computing device and on theindication of the identity of the remote computing device, establishingthe remote desktop connection with the remote computing device; andbased on the remote desktop connection, sharing a graphical userinterface of the remote computing device with the host computing deviceand the participant computing device.
 9. The method of claim 8, whereinsharing the graphical user interface of the remote computing devicecomprises communicating, from the server computer to the host computingdevice and the participant computing device, data corresponding to thegraphical user interface that is generated by the remote computingdevice for presentation at a display of the remote computing device. 10.The method of claim 9, wherein the data is used by the host computingdevice and the participant computing device to present the graphicaluser interface that is generated by the remote computing device at adisplay of the host computing device and a display of the participantcomputing device, respectively.
 11. The computer-implemented method ofclaim 8, wherein the information identifying the remote computing devicecomprises at least one of a hostname or an Internet Protocol (IP)address for the remote computing device.
 12. The computer-implementedmethod of claim 8, wherein the remote computing device comprises adesktop computer, and wherein the host computing device comprises amobile computing device.
 13. The computer-implemented method of claim 8,further comprising: at the server computer, receiving, from the hostcomputing device, an indication of an input intended for a softwareapplication executing at the remote computing device; and based on theindication of the input, communicating a command to the remote computingdevice.
 14. The computer-implemented method of claim 13, wherein thesoftware application executing at the remote computing device iscontrolled based on the input provided at the host computing device. 15.Computer storage media having computer-executable instructions embodiedthereon that, when executed by a computing device having a processor anda memory, cause the computing device to perform a method comprising:establishing a web conferencing session including a host computingdevice and a participant computing device; receiving, from the hostcomputing device, a request to establish a remote desktop connectionwith a remote computing device, the request comprising an indication ofan identity of the remote computing device, wherein the indication ofthe identity of the remote computing device is received from the hostcomputing device based on a prompt for information identifying theremote computing device; based on the request to establish the remotedesktop connection with the remote computing device and on theindication of the identity of the remote computing device, establishingthe remote desktop connection with the remote computing device; andbased on the remote desktop connection, sharing a graphical userinterface of the remote computing device with the host computing deviceand the participant computing device.
 16. The computer storage media ofclaim 15, wherein sharing the graphical user interface of the remotecomputing device comprises communicating to the host computing deviceand the participant computing device data corresponding to the graphicaluser interface that is generated by the remote computing device forpresentation at a display of the remote computing device.
 17. Thecomputer storage media of claim 16, wherein the information identifyingthe remote computing device comprises at least one of a hostname or anInternet Protocol (IP) address for the remote computing device.
 18. Thecomputer storage media of claim 16, wherein the graphical user interfacethat is generated by the remote computing device is generated based onthe remote computing device executing a software application thatresides at the remote computing device.
 19. The computer storage mediaof claim 18, wherein the software application that resides at the remotecomputing device is responsive to an input provided at the hostcomputing device.
 20. The computer storage media of claim 19, whereinthe input provided at the host computing device is provided at a touchscreen display of the host computing device and via a graphical userinterface associated with a web conferencing application executing atthe host computing device.